Repository navigation
Windows: Explicitly list versions with upper bound - #473
Merged
Merged
Conversation
savannahostrowski
approved these changes
Nov 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow on from #455.
I definitely found the change in that PR helped for the last releases: different wording like "(only up to 3.15)" is clearer than "(3.15 and earlier)", when we also have options like "(3.15 and later)".
I suggested somewhere about explicitly listing the versions, but we can't replace those like "(3.15 and later)" with "(3.15, 3.16)" because we'd have to remember to add 3.17 and so on.
But we can replace those like "(only up to 3.15)" with "(3.14, 3.15)" because it's a finite set, and it doesn't matter if we forget to remove 3.14 when it's no longer relevant.
Before:
After: